Clarify different variants of "multi-database support"#6156
Closed
Clarify different variants of "multi-database support"#6156
Conversation
gvasquezvargas
force-pushed
the
BDR-clarify-multi-db-usage
branch
from
dddee8e to
0502159
Compare
Contributor
|
@mwanner, can you have a look at the latest docs: https://www.enterprisedb.com/docs/pgd/latest/known_issues/#multiple-databases-on-single-instances and let us know if we still need to have the changes proposed in this PR? |
Contributor
Author
Clearly still no good, but needs clarification w/ PMs, IMO. I'll ditch this PR in any case. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Changed?
For PGD 5 limitations, clarify the multi-database deprecation. Indicate future plans and a work-around.